Repository navigation
Use repository token for verified Dependabot updates - #14
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Use the reviewed shared policy at 9adf87acebe1d68abf18f71af9cb1af8e3c96770 through a main-only trusted workflow. The built-in repository token is limited to the merge job; no dedicated App, Environment, private key or PAT is used. Keep verified Bot/signed compatible dependency admission and exact required PR CI. Existing repository roles and server protection remain authoritative; no bypass, release, tag or deployment is added. Generated YAML and workflow-name contracts were validated against the current main. Required owner CI must succeed before normal merge.